Google Git
Sign in
android / platform / external / apache-commons-bcel / 0189999c179acaad1449572b44c6a683d5d6b07b
commit0189999c179acaad1449572b44c6a683d5d6b07b[log] [tgz]
authorAndroid Build Coastguard Worker <android-build-coastguard-worker@google.com>Tue Dec 24 16:02:13 2024 -0800
committerAndroid Build Coastguard Worker <android-build-coastguard-worker@google.com>Tue Dec 24 16:02:13 2024 -0800
tree39e3dece6b7b48419d95c6a46a6d3491cf039963
parentb85e1e3f8ca68b94746735f84f634540f207550d [diff]
parentd451b6389cf82683388bcc4cc68071c3fc877e6c [diff]
Snap for 12847752 from d451b6389cf82683388bcc4cc68071c3fc877e6c to sdk-release Change-Id: Ia261096edb5e8f3cdb112a0df7664e19b065048b
tree: 39e3dece6b7b48419d95c6a46a6d3491cf039963
  1. docs/
  2. src/
  3. .gitignore
  4. .travis.yml
  5. Android.bp
  6. CONTRIBUTING.md
  7. LICENSE
  8. LICENSE.txt
  9. METADATA
  10. MODULE_LICENSE_APACHE2
  11. NOTICE.txt
  12. OWNERS
  13. pom.xml
  14. README.md
  15. README.version
  16. RELEASE-NOTES.txt
  17. TODO.JustIce
README.md

Apache Commons BCEL

Build Status Coverage Status Maven Central Javadocs

Apache Commons Bytecode Engineering Library

Documentation

More information can be found on the Apache Commons BCEL homepage. The Javadoc can be browsed. Questions related to the usage of Apache Commons BCEL should be posted to the user mailing list.

Where can I get the latest release?

You can download source and binaries from our download page.

Alternatively you can pull it from the central Maven repositories:

<dependency> <groupId>org.apache.bcel</groupId> <artifactId>bcel</artifactId> <version>6.3</version> </dependency>

Contributing

We accept Pull Requests via GitHub. The developer mailing list is the main channel of communication for contributors. There are some guidelines which will make applying PRs easier for us:

  • No tabs! Please use spaces for indentation.
  • Respect the code style.
  • Create minimal diffs - disable on save actions like reformat source code or organize imports. If you feel the source code should be reformatted create a separate PR for this change.
  • Provide JUnit tests for your changes and make sure your changes don't break any existing tests by running mvn clean test.

If you plan to contribute on a regular basis, please consider filing a contributor license agreement. You can learn more about contributing via GitHub in our contribution guidelines.

License

This code is under the Apache Licence v2.

See the NOTICE.txt file for required notices and attributions.

Donations

You like Apache Commons BCEL? Then donate back to the ASF to support the development.

Additional Resources